Framework for classifying an object as malicious with machine learning for deploying updated predictive models

ABSTRACT

According to one embodiment, an apparatus comprises a first analysis engine and a second analysis engine. The first analysis engine analyzes an object to determine if the object is malicious. The second analysis engine is configured to (i) receive results of the analysis of the object from the first analysis engine and (ii) analyze, based at least in part on the analysis by the first analysis engine, whether the object is malicious in accordance with a predictive model. Responsive to the first analysis engine and the second analysis engine differing in determinations as to whether the object is malicious, information associated with an analysis of the object by at least one of the first analysis engine and the second analysis engine is uploaded for determining whether an update of the predictive model is to occur. An update of the predictive model is subsequently received by the classification engine.

1. CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/579,896 filed Dec. 22, 2014, now U.S. Pat. No. 9,690,933 issued Jun. 27, 2017, the entire contents of all of which are incorporated by reference herein.

2. FIELD

Embodiments of the disclosure relate to the field of cyber security. More specifically, one embodiment of the disclosure relates to a system, apparatus and method for automatically updating a classification engine that analyzes an object and determines whether the object is to be classified as malicious.

3. GENERAL BACKGROUND

Over the last decade, network devices that access the Internet or other publicly accessible networks have been increasingly subjected to malicious attacks. These malicious attacks may simply involve the use of stolen credentials by an unauthorized person in efforts to illicitly gain access to information stored within a network device. However, other malicious attacks may be more complex.

In general, malicious attacks may be carried out via an exploit or malware. An exploit is information that attempts to take advantage of a vulnerability in computer software or systems by adversely influencing or attacking normal operations of a targeted computer

For example, malicious attacks may involve malicious software that has been downloaded by the network device. In some situations, the victim is unaware that the malicious software has been downloaded and stored within her network device. In other situations, the victim is aware that the software has been downloaded, but is unaware of its malicious activity. After being stored on the victim's network device, malicious software may, by design, compromise the network device, for example, by employing an exploit to take advantage of a software vulnerability in the network device in order to harm or co-opt operation of the network device. For instance, the malicious software may (i) gain access to certain stored information and attempt to upload such information to a targeted Command and Control (CnC) server or (ii) establish connectivity between the network device to a remote computer in efforts to exfiltrate stored information.

New malicious software is released to the Internet regularly. The speed at which attackers revise the attacks of their malicious software through code modifications requires cyber security service providers to match this speed in revising detection capabilities for these threats. For a two-stage threat detection platform, which conducts both static and dynamic analysis of incoming data, a classification engine that classifies whether the data under analysis is “malicious” (e.g., a classification that identifies a certain likelihood that the data is malicious), needs to be regularly updated to remain effective.

The classification engine is responsible for classifying data as malicious or not based on whether such data includes one or more features that already have been determined to suggest maliciousness at an associated probability level. These features may include (i) a particular file size, (ii) presence of an attachment, (iii) format type (e.g., whether the file includes an executable, a portable document format “pdf” document, etc.), (iv) specific data patterns, (v) source of the file, and (vi) a structure of the file. Reliance on manually initiated updates for the classification engine tends to be problematic as these updates are not regularly provided, due to human error in some cases. A technique is needed that will automatically update the detection capabilities of the classification engine with a reduced update cycle time.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is an exemplary block diagram of a sequence of operations for a threat detection platform.

FIG. 2 is an exemplary block diagram of a communication system deploying one or more threat detection platforms (TDPs) communicatively coupled to a management system.

FIG. 3 is an exemplary block diagram of logic associated with the TDP of FIG. 2.

FIG. 4 is an exemplary block diagram of logic associated with the classification testing system of FIG. 2.

FIGS. 5A-5C are general exemplary flowcharts that illustrates operation conducted by an electronic device for determining and conducting an update of a classification engine.

FIG. 6 is an exemplary embodiment of an endpoint device including a security agent that conducts the classification engine update scheme as described in FIG. 1.

DETAILED DESCRIPTION

Various embodiments of the disclosure relate to a framework which, based upon the threats detected, periodically, aperiodically, or continuously updates a classification engine to better recognize the presence of malicious software and/or exploits (referred collectively referred to herein as “malware”) within analyzed objects. This framework features a training engine that, based on information associated with detected threats, automatically (and without user intervention) issues an alert when the classification engine requires updating. Once the alert is issued by the training engine, one or more parameters (e.g., particulars to an analyzed feature of the object, including score, weighting, string length, bit size, character type, etc.) within a predictive model are modified (e.g., added, deleted and/or changed). The “predictive model” is logic that controls the analysis conducted by a classification engine, and modification of the predictive model is conducted to reduce the number or rate of false negative events by the classification engine.

As described herein, the classification engine may be deployed for classifying an object as malicious or not malicious based on static analysis results, although inventive aspects set forth in the disclosure may also be employed to automatically update a classification engine operating on behaviors observed during run-time analysis or operating on both static analysis results and observed behaviors.

I. DETAILED SUMMARY

According to one embodiment of the disclosure, logic is provided to enhance operability of a classification engine by evaluating results in the analysis of an object by that classification engine operating in accordance with a current predictive model. This logic, referred to herein as a “training engine,” conducts this evaluation in order to determine whether the current predictive model needs updating to more accurately classify whether an object (e.g., any collection of data including a file, document, web page, etc.) is “malicious” (e.g., varying in degree from definitely malicious to a level where the object is suspected to be malicious, sometimes referred to as “suspicious”), or benign (non-malicious). Additionally, the training engine is configured to automatically generate an updated predictive model (hereinafter referred to as a “reference model”) based on actual feature(s) of the suspect object.

Herein, the type of triggering event that causes the feature(s) of the suspect object to be provided to the training engine may vary, depending on the desired involvement of the training engine in the modification of the classification engine. As an example, one triggering event may be based on identifying a disagreement as to whether an object under analysis is malicious between a detection engine and a classification engine within the same security appliance (herein referred to as a “threat detection platform”). The disagreement may be based on difference in the degree (or level) of detected “maliciousness” or “non-maliciousness” (e.g., malicious v. non-malicious, detected “malicious” levels differ, etc.). According to this embodiment of the disclosure, the detection engine and the classification engine correspond to the same analysis engine (e.g., static analysis engine or the dynamic analysis engine as illustrated in FIG. 2).

Another triggering event may be based on outputted results from a collective classification engine that receives results from one of more of the analysis engines (e.g., detection engines from the static analysis engine and/or the dynamic analysis engine). Herein, the collective classification engine generates a result that identifies, for reporting purposes, whether the object under analysis is malicious—the triggering event may occur when the result fails to accurately identify the level of maliciousness for that object. For example, the collective classification engine may determine a confidence score (X) that barely classifies the object as “malicious”, and the triggering event occurs when the confidence score (X) deviates from a predetermined confidence score (X+Y or X−Y) by a prescribed threshold (e.g., less than a maximum confidence score (X+Y) by the prescribed threshold (Z, Z<Y) or greater than a set confidence score (X−Y) by less than the prescribed threshold (Z, Z>Y)).

For instance, as an illustrative embodiment, the training engine may be deployed to receive features associated with a suspect object that is considered to be “malicious” by a detection engine. In this embodiment, deployed within a static analysis engine, the detection engine conducts static analysis such as exploit-specific checks, vulnerability-specific checks or rule-based checks or checks based upon emulation for example, to determine whether the analyzed object includes one or more features that suggest that the object is “malicious” (e.g., indicates that there exists at least a prescribed probability that the one or more features may be associated with a malicious attack).

Where the detection engine determines that the suspect object may include one or more malicious features, but the classification engine using the current predictive model for analysis classifies the object as non-malicious (e.g., assigns a confidence value that falls below a certain threshold), this denotes a potential false negative event. As a result, the threat detection platform transmits a control message to the training engine, where the control message may include (1) an identifier of the object (e.g., hash value of the object), (2) one or more suspect features of the object that can be used by the predictive model to classify the file as malicious, and/or (3) results from the preliminary classification of the suspect object by this platform-based classification engine (e.g., confidence values). Concurrently, where the disagreement between the detection engine and the classification engine occurs in the static analysis engine, the object and perhaps the results from the detection engine may be provided to a virtual execution environment within the threat detection platform for dynamic analysis.

Otherwise, when the object is determined to be malicious by both the detection engine and the (platform-based) classification engine associated with the static analysis engine, the object under analysis is provided to the virtual execution environment without initiating a triggering event.

Potentially located outside the enterprise and accessible by a cyber-security service provider, the training engine receives the identifier of the suspect object (e.g., hash value of the object) to determine if the object has been evaluated previously in accordance with the current predictive model. If not, the training engine may modify one or more parameters associated with the current predictive model to better detect those feature(s) associated with the suspect object that have been determined to be malicious by the detection engine as described above. This modification may involve altering parameters by changing certain values in a decision-tree analysis associated with the current predictive model, which produces an updated predictive (reference) model.

As an illustrative example, the modification of the current predictive model may include changing character string values associated with a name of the object, which may signify the object is malicious. These character string values may include, but are not limited or restricted to length or character types. Another modification may include increasing values (e.g., confidence scores) that are assigned to certain types of features to decrease the number (or rate) of false negative events, or may involve decreasing values assigned to certain types of features to reduce the number (or rate) of false positive events. Additionally, modification may further involve adding or deleting analytical operations from the decision-tree analysis of the current predictive model (e.g., adding/removing certain analysis, etc.).

Based at least in part on the results from the preliminary classification by the platform-based classification engine (e.g., confidence values), which over time identifies whether the current predictive model is ineffective or is becoming less effective in detecting malicious attacks, an alert is provided from the training engine to update a reference classification engine accessible by the cyber security service provider along with one or more platform-based classification engines with the reference model.

It is contemplated that the classification engines may be updated based on analysis and classificaiton of objects conducted by other security appliances (for a more holistic view of malware features) and of forensic work by expert analysts and laboratories. As a result, the reference model is not modified based solely on objects uploaded by a single security appliance.

II. TERMINOLOGY

In the following description, certain terminology is used to describe features of the invention. For example, in certain situations, both terms “engine,” “component” and “logic” are representative of hardware, firmware and/or software that is configured to perform one or more functions. As hardware, engine (or component/logic) may include circuitry having data processing or storage functionality. Examples of such circuitry may include, but is not limited or restricted to a microprocessor, one or more processor cores, a programmable gate array, a microcontroller, an application specific integrated circuit, wireless receiver, transmitter and/or transceiver circuitry, semiconductor memory, or combinatorial logic.

Engine (or component/logic) may be software in the form of one or more software modules, such as executable code in the form of an executable application, an application programming interface (API), a subroutine, a function, a procedure, an applet, a servlet, a routine, source code, object code, a shared library/dynamic load library, or one or more instructions. These software modules may be stored in any type of a suitable non-transitory storage medium, or transitory storage medium (e.g., electrical, optical, acoustical or other form of propagated signals such as carrier waves, infrared signals, or digital signals). Examples of non-transitory storage medium may include, but are not limited or restricted to a programmable circuit; a semiconductor memory; non-persistent storage such as volatile memory (e.g., any type of random access memory “RAM”); persistent data store such as non-volatile memory (e.g., read-only memory “ROM”, power-backed RAM, flash memory, phase-change memory, etc.), a solid-state drive, hard disk drive, an optical disc drive, or a portable memory device. As firmware, the executable code is stored in persistent storage.

The term “object” generally refers to a collection of data, whether in transit (e.g., over a network) or at rest (e.g., stored), often having a logical structure or organization that enables it to be classified for purposes of analysis. During analysis, for example, the object may exhibit a set of expected features and, during processing, a set of expected behaviors. The object may also exhibit a set of unexpected features and a set of unexpected behaviors that may evidence malware and potentially allow the object to be classified as malware.

The term “model” generally refers to logic that is used in classifying an object under analysis as malicious or not. One type of model includes a predictive model, which may be logic in the form of a decision-tree based analysis in which parameters associated with the analysis or certain decisions may be modified in order to “tune” the analysis to improve performance.

The term “transmission medium” is a physical or logical communication path between two or more electronic devices (e.g., any devices with data processing and network connectivity such as, for example, a security appliance, a server, a mainframe, a computer such as a desktop or laptop, netbook, tablet, firewall, smart phone, router, switch, bridge, etc.). For instance, the communication path may include wired and/or wireless segments, and/or shared memory locations. Examples of wired and/or wireless segments include electrical wiring, optical fiber, cable, bus trace, or a wireless channel using infrared, radio frequency (RF), or any other wired/wireless signaling mechanism.

The term “computerized” generally represents that any corresponding operations are conducted by hardware in combination with software and/or firmware.

Lastly, the terms “or” and “and/or” as used herein are to be interpreted as inclusive or meaning any one or any combination. Therefore, “A, B or C” or “A, B and/or C” mean “any of the following: A; B; C; A and B; A and C; B and C; A, B and C.” An exception to this definition will occur only when a combination of elements, functions, steps or acts are in some way inherently mutually exclusive.

The invention may be utilized for updating classification engines. As this invention is susceptible to embodiments of many different forms, it is intended that the present disclosure is to be considered as an example of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described.

III. CLASSIFICATION ENGINE UPDATE SCHEME

Referring to FIG. 1, an exemplary block diagram of a sequence of operations for threat detection within a system that is configured to detect malicious attacks is shown. The system 100 may broadly include a plurality of components, namely a processing engine 110, one or more analysis engines 115, a training engine 130, and a reference classification engine 140. According to this embodiment, the processing engine 110 and the analysis engine(s) 115 operate on a security appliance (referred to as “threat detection platform”) located within an enterprise while the training engine 130 and the reference classification engine 140 may operate as cloud computing services for example, may operate in a different enterprise, or may operate within the same enterprise as the processing engine 110 and analysis engine(s) 115.

Located in the threat detection platform 150, the processing engine 110 receives an object and converts that object into a format, as needed or appropriate, on which deep scanning by at least a first analysis engine 120 can be applied. This conversion and scanning may involve decompression of the object, decompilation of the object, extraction of specific data associated with the object, and/or emulation of the extracted data (like Javascript).

Located in the threat detection platform 150 as part of the first analysis engine 120 (e.g., static analysis engine), a first detection engine 122 is configured to conduct exploit-specific checks, vulnerability-specific checks and/or rule-based checks on the data associated with the object, as described below. Based on the results of the check(s), the first detection engine 122 may uncover one or more features that may indicate that the suspect object is malicious. These features may also be supplied to a first, platform-based classification engine 124 that determines, based on analysis of the feature(s) given its predictive model, whether the suspect object is malicious or not.

According to one embodiment of the disclosure, in response to a triggering event, such as where the object is determined to be malicious by the first detection engine 122, but is classified by the first classification engine 124 as non-malicious, information associated with the object may be provided to the training engine 130. It is contemplated that this triggering event may occur in response to this discrepancy or may be programmed for throttling the triggering event based on the degree of discrepancy, the rate or periodicity of discrepancies, or the number of times that the discrepancy occurs. When provided, this object information may include, but is not limited or restricted to (1) an identifier 126 of the object (e.g., hash value of the object such as a message digest produced in accordance with Message Direct “MD5” algorithm), (2) one or more features 127 of the suspect object that are associated with a malicious attack, and/or (3) results 128 of the preliminary classification by the first classification engine 124 (e.g., confidence values). Concurrently, the object and results in the preliminary analysis by the first analysis engine 120 are provided to a second analysis engine 160.

Of course, it is contemplated that, where the object is determined to be non-malicious (or malicious) by both the first detection engine 122 and the first classification engine 124, the object and results are merely provided to the second (dynamic) analysis engine 160. The training engine 130 is to receive information where the analysis results from the first detection engine 122 and the first classification engine 124 differ as to whether the object under analysis is malicious or not. However, according to another embodiment of the disclosure, this difference in analysis may occur when the suspect object is determined to be malicious by both the first detection engine 122 and the first classification engine 124, but the confidence score produced by the first classification engine 124 falls below a prescribed score threshold.

Located remotely from the threat detection platform 150, such as part of a cloud computing service or within a different enterprise network for example, the training engine 130 is configured to receive an identifier for the object in order to determine if the object has been previously analyzed in a potential update of the current predictive model. If not, the training engine 130 makes use of one or more features of the suspect object from the first detection engine 122 to determine if the object is malicious and determines which portions within the current predictive model need to be modified to better detect such features for classifying files as malicious.

There exist a few schemes that may be used by the training engine 130 to determine when an alert should be issued to update the current predictive model used by the reference classification engine 140 and/or platform-based classification engine(s) 124 and/or 164. For instance, the training engine 130 may rely on the received confidence score from the first classification engine 124 to determine accuracy in classifying a detected malicious object. In response to consistent false negative events by the classification engine 124 (e.g., the detected false negative events exceed a certain number or a prescribed rate) or a prescribed period of time has elapsed between updates, the training engine 130 may issue signaling, referred to as an “alert,” to update the reference classification engine 140 and/or platform-based classification engines 124 and/or 164 deployed at the customer. According to one embodiment, the reference model is generated as part of the cloud computing services or as part of services for an enterprise.

Similarly, the training engine 130 may issue an alert to update the reference classification engine 140 and subsequently platform-based classification engines 124/164 within the TDP(s) when an average confidence score for different objects that are detected as malicious by the first detection engine 122 (but are considered non-malicious by the first classification engine 124), as measured over a prescribed period of time, falls below a minimum detection threshold. Alternatively, the training engine 130 may issue an alert in response to a series of confidence scores for different objects that are detected as malicious by the first detection engine 122 (but are considered non-malicious by the platform-based classification engine 124) are consistently decreasing (over a prescribed period of time) by a certain amount (or percentage). As yet another alternative, the training engine 130 may prompt the reference classification engine 140 to analyze one or more features associated with a subsequent object under analysis using the reference model and determine whether the resultant confidence score exceeds the received confidence score by a prescribed amount (in value or in percentage).

Located as a cloud computing service or within a separate enterprise network or within the same enterprise network but at a different location as TDP 150 for this embodiment, the reference classification engine 140 receives the reference model (updated predictive model) produced by the training engine 130 or receives specific updates that are applied to the current reference model by the reference classification engine 140 to produce the reference model. According to one embodiment of the disclosure, the reference model is returned to the threat detection platform 150 to update the classification engine 124 that classifies analytic results associated with the first detection engine 122 of the static analysis engine 120. Additionally, or in the alternative, the reference model may be returned to the threat detection platform 150 to update a classification engine 164 associated with the second analysis engine 160, or any other platform-based classification engine, as described below in further detail.

Of course, it is contemplated that object classification associated with the static analysis results may be handled as cloud computing services without deployment of the first classification engine 124. For this embodiment, information associated with malicious objects would be uploaded to the reference (cloud-based) classification engine 140. The reference classification engine 140 would determine whether information needs to be provided to the training engine 130 for modification of the predictive model associated with the classification engine. The reference model also may be returned to another classification engine within the TDP 150 for subsequent classification of the suspect object by the second (dynamic) analysis engine 160.

IV. EXEMPLARY SYSTEM ARCHITECTURES

Referring to FIG. 2, an exemplary block diagram of a communication system 200 deploying one or more threat detection platforms (TDPs) 150 ₁-150 _(N) (N>1, N=3 for this embodiment) communicatively coupled to a management system 205 via a network 210 is shown. In general, the management system 205 is adapted to manage TDPs 150 ₁-150 ₃. While cloud computing services 230 (or services via a separate enterprise) may be responsible for updating predictive models utilized by one or more classification engines deployed within the TDP 150 ₁, the management system 205 is responsible for updating software utilized by the TDPs 150 ₁-150 ₃. Such updating may be conducted automatically or conducted manually via uploads by an administrator. Also, such updating may be conducted freely among the TDPs 150 ₁-150 ₃ or subject to a subscription basis in which periodic or aperiodic updates of the predictive model are provided by a service including the classification testing system 235.

Herein, according to the embodiment illustrated in FIG. 2, a first TDP 150 ₁ is an electronic device that is adapted to analyze information associated with network traffic from at least one network device 212 for transmission over a communication network 214, such as communications with server. The communication network 214 may include a public network such as the Internet, in which case an optional firewall 216 (represented by dashed lines) may be interposed prior to accessing another network device 220. Alternatively, the communication network 214 may be a private network such as a wireless data telecommunication network, wide area network, a type of local area network (LAN), or a combination of networks.

As shown, the first TDP 150 ₁ may be communicatively coupled with the communication network 214 via an interface 218. In general, the interface 218 operates as a data capturing device (sometimes referred to as a “tap” or “network tap”) that is configured to receive data propagating to/from the network device 220 within an enterprise network and provide at least some of this data to the first TDP 150 ₁ or a duplicated copy of the data. Alternatively, although not shown in detail, the first TDP 150 ₁ may be positioned behind the firewall 216 and at least partially in-line with network (client) device 220 so as to subject incoming traffic to analysis (e.g., through static analysis) and potentially block that which is classified as malware from reaching its destination.

According to an embodiment of the disclosure, the interface 218 may be further configured to capture metadata from network traffic associated with network device 220. According to one embodiment, the metadata may be used, at least in part, to determine protocols, application types and other information that may be used by logic within the first TDP 150 ₁ to determine particular software profile(s). The software profile(s) are used for selecting and/or configuring one or more virtual machines 285 ₁-285 _(M) (M≥1) within a run-time, virtual execution environment 162 of the dynamic analysis engine 160, as described below. These software profile(s) may be directed to different software or different versions of the same software application extracted from software image(s) fetched from storage device 270.

In some embodiments, interface 218 may provide connectivity to a server or any device with storage capability through a dedicated transmission medium such as a wireless channel, a wired cable or the like. Although not shown, interface 218 may be contained within the first TDP 150 ₁. In other embodiments, the interface 218 can be integrated into an intermediary device in the communication path (e.g., firewall 216, router, switch or other networked electronic device, which in some embodiments may be equipped with SPAN ports) or can be a standalone component, such as an appropriate commercially available network tap.

As further shown in FIG. 2, the first TDP 150 ₁ comprises processing engine 110, the first (static) analysis engine 120, a scheduler 265, a storage device 270, a second (dynamic) analysis engine 160, reporting engine 290 with an optional user interface capability, and/or a collective platform-based classification engine 295. The first TDP 150 ₁ operates in combination with the classification testing system 235, which includes the training engine 130, by uploading information that may assist the training engine 130 in determining whether logic within the classification engine 124, 164 and/or 295 requires updating. The logic may include a predictive model, namely decision-tree learning logic at least partially developed using machine learning techniques from prior analysis of labelled and unlabeled malware, benign objects and/or experiential knowledge from human analysts that determines whether feature(s) of the suspect object indicate that the object is malicious (e.g., associated with a particular malware).

The processing engine 110 of the first TDP 150 ₁ is configured to receive an incoming object 240 (operation 1) and to convert the object 240 into a format that may be subsequently analyzed by the static analysis engine 120 to determine if the object 240 includes one or more features that are considered potentially associated with malicious activity. This conversion may involve decompression and/or decompilation of the object 240, extraction of specific data of the object 240, and/or emulation of the extracted data.

The static analysis engine 120 comprises a controller 250, a first data store 252, the detection engine 122, object transformation logic 258 and the first classification engine 124. The controller 250 is logic that controls operations conducted within the static analysis engine 120. These operations may include data storage within first data store 252; pattern matching of the incoming object 240 to determine whether the object 240 includes one or more malicious features; preliminary classification of the object 240; and/or cryptographic operations on the object 240, including one-way hash operations.

Herein, the static analysis engine 120 includes the detection engine 122 that includes one or more software modules that, when executed by controller 250, analyzes features for the incoming object 240 (e.g., a portion of network traffic, an uploaded file, etc.). As such, the detection engine 122 analyzes the object 240 through one or more pattern checking operations without execution of the object 240. Examples of the pattern checking operations may include signature matching 255 to conduct (a) exploit signature checks, which may be adapted to compare at least a portion of the object 240 with one or more pre-stored exploit signatures (pre-configured and predetermined attack patterns) from signature database (not shown), and/or (b) vulnerability signature checks that may be adapted to uncover deviations in messaging practices (e.g., non-compliance in communication protocols, message formats or ordering, and/or payload parameters including size). Other examples of these pattern checking operations may include (i) heuristics 256, which is based on rules or policies as applied to the object and may determine whether one or more portions of the object 240 is associated with an anomalous or suspicious feature (e.g., a particular URL associated with known exploits, or a particular source or destination address etc.) associated with known exploits; or (ii) determinative rule-based analysis 257 that may include blacklist or whitelist checking.

After operations are conducted by the detection engine 122 to uncover potentially malicious features in the object 240, the classification engine 124 determines whether this object 240 is “malicious,” namely whether certain features of the object 240 suggest an association with a malicious attack. According to one embodiment of the disclosure, in addition (or in the alternative) to being stored in the first data store 252, some or all of results produced by the detection engine 122 may be provided to the first classification engine 124, which is configured to determine a probability (or level of confidence) that the suspect object 240 is malware.

More specifically, the first classification engine 124 may be configured to determine a probability (or level of confidence) that the object 240 is associated with a malicious attack. This probability may be represented through a value (referred to as a “static analysis confidence score”) that may be used by the training engine 130 to identify the need for updating the predictive model utilized by the first classification engine 124. The static analysis confidence score may be determined based, at least in part, on (i) the particular pattern matches; (ii) heuristic or determinative analysis results; (iii) analyzed deviations in messaging practices set forth in applicable communication protocols (e.g., HTTP, TCP, etc.); (iv) analyzed compliance with certain message formats established for the protocol (e.g., out-of-order commands); and/or (v) analyzed header or payload parameters to determine compliance

Furthermore, the static analysis engine 120 may route this suspect object 240 (or specific portions or features of the suspect object 240) to the dynamic analysis engine 160 for more in-depth analysis. Also, results 253 of the static analysis may be stored within the first data store 252. The static analysis results 253 may include (i) a static analysis confidence score (described above) and/or (ii) metadata associated with the object. The metadata may include (a) features associated with malware (e.g., matched signature patterns, certain heuristic or statistical information, etc.), and/or (b) other types of metadata associated with the object under analysis (e.g., name of malware or its family based on the detected exploit signature, anticipated malicious activity associated with this type of malware, etc.).

After analysis of the object, the static analysis engine 120 may route the suspect object 240 to the dynamic analysis engine 160, which is configured to provide more in-depth analysis by analyzing the suspect object in a VM-based operating environment. Although not shown, the suspect object 240 may be buffered by the first data store 252 or a second data store 282 until ready for processing by virtual execution environment 162. Of course, if the object 240 is not suspected of being part of a malicious attack, the static analysis engine 120 may denote that the object is benign, and thus, refrain from passing information associated with object 240 to the training engine 130. Instead, the object 240 is passed to the dynamic analysis engine 160 for subsequent analysis.

More specifically, after analysis of the features of the suspect object 240 has been completed (or after analysis of multiple suspect objects where certain features are buffered), the static analysis engine 120 may provide at least some or all of the features that are identified as being potentially associated with malware, to the training engine 130 for determination as to whether updating of the first classification engine 124 (and/or any other classification engine 140, 164 and/or 295) is necessary. According to one embodiment of the disclosure, the static analysis engine 120 provides (1) an identifier (e.g., hash value) of the suspect object 240, (2) one or more suspect features of the suspect object 240 and/or (3) some or all of the results 253 from the static analysis, which may include static analysis confidence value. The upload of this information is identified by operations 3-4.

Located outside an enterprise featuring the TDP 150 ₁, the training engine 130 receives the identifier 126 of the object (e.g., hash value of the object) to determine if the object has been evaluated previously in accordance with the current predictive model. This may be accomplished by comparing a listing of identifiers maintained by the training engine 130, where each identifier represents an object whose features have already been evaluated in updating the current predictive model. If the suspect object 240 has been previously evaluated, the training engine 130 may disregard such features or further adjust parameters within the updated current predictive (reference) model given that there are repeated occurrences of this type of malicious object or the object now includes different features that have not been considered.

If the object has not been previously evaluated, the training engine 130 analyzes the results, and based on the analysis, may modify one or more parameters associated with the reference model to better detect the one or more features associated with the received object that have been determined to be malicious by the static analysis engine 120 as described above. Determined through analysis of the results 253 from the static analysis engine 120, this parameter modification may include changing certain values in the decision-tree analysis as provided by the current predictive model.

As an illustrative example, suppose that the filename analysis in the current predictive model is represented by the following in which a score of 80 out of a maximum 100 is applied if the name of the object is greater than 15 characters and does not begin with an alphanumeric character (A-Z or 0-9):

-   -   if length_of_string (string)>15         -   if first_char≠char ‘[A-Z]’         -   if first_char≠‘[0-9]’     -   score=80         The parameter modification may involve altering the length of         the string parameter, checking for first character, etc. upon         the training engine 130 determining that this feature (e.g.,         name length and/or character string types) has a higher         correlation to maliciousness than previously assigned. In         combination with or in the alternative, the parameter         modification may involve removal of the first character “0” as         suspect objects that have been received by the training engine         130 are now tending to include the “0” at the start of the         object name.

Based at least in part on the static analysis confidence values, which over time identifies whether the current predictive model remains ineffective or is becoming less effective, an alert is provided from the training engine 130 to update the reference classification engine 140, which is immediately accessible by the cyber security service provider. The reference classification engine 140 may be used to update platform-based classification engines (e.g., classification engine 124, 164 and/or 295) with the reference model as illustrated in operation 5. Of course, it is contemplated that the TDP 150 ₁ may not feature any platform-based classification engines, and in this type of deployment, the reference classification engine 140 would only need to be updated.

Referring still to FIG. 2, in one embodiment of the disclosure, the scheduler 265 may be adapted to configure one or more VMs 285 ₁-285 _(M) based on metadata associated with a flow that includes the object under analysis. For instance, the VMs 285 ₁-285 _(M) may be configured with software profiles corresponding to the software images stored within storage device 270. As an alternative embodiment, the VMs 285 ₁-285 _(M) may be configured according to one or more software configurations that are being used by electronic devices connected to a particular enterprise network (e.g., network “client” device(s) 220) or prevalent types of software configurations (e.g., a Windows® 7 OS; a certain version of a particular web browser such as Internet Explorer®; Adobe® PDF™ reader application). As yet another alternative embodiment, the VMs 285 ₁-285 _(M) may be configured to support concurrent (e.g. at least partially simultaneous in time) virtual execution of a variety of different software configurations in efforts to verify that the suspicious object is part of a malicious attack. Of course, it is contemplated that the VM configuration described above may be handled by logic other than the scheduler 265.

According to one embodiment of the disclosure, the dynamic analysis engine 160 is adapted to execute one or more VMs 285 ₁-285 _(M) to simulate the receipt and execution of content associated with the object under analysis within a run-time environment as expected by the type of object. For instance, dynamic analysis engine 160 may optionally include processing logic 280 to emulate and provide anticipated signaling to the VM(s) 285 ₁, . . . , and/or 285 _(M) during virtual processing.

For example, the processing logic 280 may be adapted to provide, and sometimes modify (e.g., modify IP address, etc.) packets associated with the suspect object 240 in order to control return signaling back to the virtual execution environment 162. Hence, the processing logic 280 may suppress (e.g., discard) the return network traffic so that the return network traffic is not transmitted to a network providing connectivity to the network (client) device 220.

Although not shown in FIG. 2, monitoring logic within the virtual execution environment 162 may be configured to monitor behaviors of one or more VMs 285 ₁, . . . , and/or 285 _(M), such as VM 285 ₁ configured to execute the suspect object 240. This monitoring is conducted to detect anomalous (e.g., unexpected, irregular, etc.) activity indicative of malware. When anomalous activity is detected, the monitoring logic operating with the second classification engine 164 to compute a dynamic analysis confidence score and provide VM-based results 288 (e.g., dynamic analysis confidence score, information associated with the detected anomalous behaviors, and/or other information associated with the detected malicious activity by the suspect object) to the platform-based classification engine 295.

It is noted that the second classification engine 164 may not be implemented within the dynamic analysis engine 160. Instead, the platform-based classification engine 295 receives the VM-based results 288 (without the dynamic analysis confidence score) and conducts a classification of the object based on the VM-based results and/or SA results (or static analysis confidence value). It is contemplated that the confidence score produced by the VM-based results 288 may be weighted differently than the static analysis confidence score.

In general, the collective platform-based classification engine 295 may be configured to receive the VM-based results 288. According to one embodiment of the disclosure, the classification engine 295 comprises prioritization logic 296 and score determination logic 297. The prioritization logic 296 may be configured to apply weighting to VM-based results 288 and/or static analysis-based results 260 from static analysis engine 120. According to one embodiment, these VM-based results 288 may include the dynamic analysis confidence score and/or the SA-based result 260 may include the static analysis confidence score.

The score determination logic 297 comprises one or more software modules that are used to determine a final probability as to whether the suspect object 240 is malicious, and the resultant score representative of this final probability may be included as part of results provided to the reporting engine 290 for reporting. The score determination logic 297 may rely on the predictive model (or updated predictive model provided as the reference model) to determine the score assigned to the object.

Herein, the reporting engine 290 generates reports (e.g., various types of signaling such as messages including text messages and email messages, display images, or other types of information over a wired or wireless communication path) to identify to a network administrator the presence of a detected suspect object in the received network traffic. The reports may include a detailed summary of at least the malware detected by the TDP 150 ₁.

Although the illustrative embodiment describes the updating of the predictive model for the classification engine 124 within the static analysis engine, it is contemplated that the similar operations may be conducted for the classification engine 164 of the dynamic analysis engine 160 and/or the collective classification engine, where the results from the detection engines of the static analysis engine 140 and/or dynamic analysis engine 160 is in disagreement and the result of the classification engine 295.

V. EXEMPLARY LOGIC LAYOUT OF TDP

Referring now to FIG. 3, an exemplary block diagram of logic associated with TDP 150 ₁ of FIG. 2 is shown. TDP 150 ₁ comprises one or more processors 300 that are coupled to communication interface logic 310 via a first transmission medium 320. Communication interface logic 310 enables communications with other TDPs 150 ₂-150 ₃ and management system 205 of FIG. 2. According to one embodiment of the disclosure, communication interface logic 310 may be implemented as a physical interface including one or more ports for wired connectors. Additionally, or in the alternative, communication interface logic 310 may be implemented with one or more radio units for supporting wireless communications with other electronic devices.

Processor(s) 300 is further coupled to persistent storage 340 via transmission medium 330. According to one embodiment of the disclosure, persistent storage 340 may include (a) static analysis engine 120, including the first detection engine 122 and the first classification engine 124; (b) the dynamic analysis engine 160 that comprises the second detection engine 162 that includes the virtual execution environment and the second classification engine 164; (c) the platform-based classification engine 295 including prioritization logic 296, score determination logic 297; (d) reporting engine 290; and (e) data stores 252 and 282. Of course, when implemented as hardware, one or more of these logic units could be implemented separately from each other. The engines contained within persistent storage 340 are executed by processor(s) and perform operations as described above.

VI. EXEMPLARY LOGIC LAYOUT OF CLASSIFICATION TESTING SYSTEM

Referring now to FIG. 4, an exemplary block diagram of logic associated with the classification testing system 235 of FIG. 2 is shown. The classification testing system 235 comprises a housing 405 that at least partially encases one or more processors 400, which are coupled to communication interface logic 410 via a first transmission medium 420. Communication interface logic 410 enables communications with one or more TDPs (e.g., TDP 150 ₁) to receive information associated with the suspect object for adjustment of logic associated with classification engine 140 and/or classification engines deployed with the TDP 150 ₁. According to one embodiment of the disclosure, communication interface logic 410 may be implemented as a physical interface including one or more ports for wired connectors. Additionally, or in the alternative, communication interface logic 410 may be implemented with one or more radio units for supporting wireless communications with other electronic devices.

Processor(s) 400 is further coupled to persistent storage 440 via transmission medium 430. According to one embodiment of the disclosure, persistent storage 440 may include (a) training engine 130, including object comparison logic 450, parameter modification logic 455 and model comparison logic 460; (b) the reference classification engine 140; (c) reference model update logic 465; and (d) data store 470. Of course, when implemented as hardware, one or more of these logic units could be implemented separately from each other.

Herein, executed by the processor(s) 400, the training engine 130 receives an identifier of the object and activates the object comparison logic 450 to determine if the object has been evaluated previously in accordance with the current predictive model. The object comparison logic 450 maintains a listing of identifiers that represent those objects for which features have been evaluated in an update of the current predictive model.

If the object is determined by the object comparison logic 450 to have been previously evaluated in generation of the reference model 475, the parameter modification logic 455 may disregard such features or further adjust parameters within a current predictive model 480 (e.g., decision-tree analysis) given that there are repeated occurrences of this type of malicious object. If the object has not been previously evaluated in generation of the reference model 475, the parameter modification logic 455 analyzes the static analysis results of the object, and based on these results, may modify one or more parameters associated with the current predictive model 480 in generation of the reference model 475 to better detect malicious objects with these types of features. Examples of parameter modifications may include changing certain values in the decision-tree analysis as provided by the current predictive model.

Upon the model comparison logic 460 determining that the current predictive model 480 remains ineffective in detecting malicious objects or is becoming less effective in detecting malicious objects, an alert is provided to the reference model update logic 465 to update the current predictive model 480 by substitution of the reference model 475 at the reference classification engine 140 (or provide the updates 485 as represented as an optional feature by dashed lines). Furthermore, reference classification engine 140 may propagate the reference model 480 to other classification engines, including classification engine 124 and 164 that are utilized by the analysis engines 120 and 160 as well as platform-based classification engine 295.

VII. EXEMPLARY THREAT DETECTION AND PREVENTION PROCESSES

Referring to FIG. 5A, a general exemplary flowchart is shown that illustrates operations conducted by an electronic device, such as a TDP or a portable device of FIG. 6 for example, for determining whether an update of the classification engine may be warranted. Upon receiving a suspect object, an analysis is conducted to determine whether the results produced by different engines in analyzing the same object for malicious features represent a false negative result, which suggests that a potential update of the classification engine is warranted (blocks 500 and 510). More specifically, this analysis may involve (i) a first analysis by a detection engine that determines whether an object under analysis is malicious and (ii) a second analysis by the classification engine that determines either (a) the suspect object is non-malicious or (b) the suspect object is malicious but the degree of malicious falls below a prescribed threshold. Based on the analysis associated with the object, if there are no potential false negative events in the analysis, no modification of the classification engine is needed.

If the analysis denotes a potential false negative event, information associated with the analysis of the object is provided to a training engine to determine whether the classification engine should be updated (block 520). As described above, this information may include, but is not limited or restricted to (1) the identifier of the object (e.g., hash value of the object such as a message digest produced in accordance with Message Direct “MD5” algorithm), (2) one or more suspect features of the object and/or (3) results of the preliminary classification by the classification engine (e.g., confidence values).

Thereafter, as shown in FIG. 5B, without user intervention and when an update of the classification engine is needed, the TDP automatically receives a reference model, namely an updated predictive model, which is used to modify the functionality of the classification engine (block 530). Upon receipt, the classification engine is updated with the reference model (block 540).

Referring now to FIG. 5C, a general exemplary flowchart is shown that illustrates a process for determining whether the update of the classification engine is warranted. First, a training engine receives information associated with the suspect object that is associated with a preliminary false negative event (block 550). Stated differently, the training engine receives one or more features of the object where a detection engine determined that the object includes malicious features, but the classification engine determined that the suspect object is non-malicious or is malicious but the degree of malicious falls below a prescribed threshold. As described above, this information may include, but is not limited or restricted to (1) an identifier of the object (e.g., hash value of the object such as a message digest produced in accordance with Message Direct “MD5” algorithm), (2) one or more suspect features of the object and/or (3) results of the preliminary classification by the classification engine (e.g., confidence values).

Thereafter, the training engine determines whether the suspect object is included in a training data set that is used to produce a current predictive model (block 555). This may involve a comparison of the provided identifier to a list of identifiers representing those objects that have been analyzed in determination of the current predictive model. If not, a secondary determination is made as to whether there exist certain features of the suspect object that were not present in any of the prior objects considered in generation of the current predictive model (block 560). If the objects include different features for analysis or the suspect object is not part of the training set data used to produce the current predictive model, the training data set is updated with the different features, along with different weighting and/or scores (block 565). Otherwise, the training data set is not updated.

Thereafter, the current predictive model is updated using the updated training data set to produce the reference model (block 570). Using at least part of the information received with the feature(s) of the suspect object, if the level of effectiveness of the current predictive model falls below a particular threshold (e.g., number of false negative events is now greater than a preset number, confidence values for detected malicious features falls below a set value, etc.), the classification engine is updated with the reference model (blocks 575, 580 and 585). Otherwise, the classification engine continues to utilize the current predictive model for classification of suspect objects as malicious or not (block 590).

It is contemplated that the classification engine update scheme, as described above, may also be conducted by a security agent 600 as shown in FIG. 6. Herein, the security agent 600 is stored within a memory 610 encased within a housing 625 of an endpoint device 620. Upon execution by a processor 630, the security agent 600 activates a static analysis engine 635 to conduct a static analysis of at least a portion of information 640 received by a transceiver 650 of the endpoint device 620. As before, in response to the static analysis engine and the classification engine 660 reaching different determinations (or the same determinations with results that exceed a certain difference threshold), security agent 600 uploads the control message including the one or more malicious features to a training engine located as part of cloud computing services or residing within a particular enterprise network (not shown). Thereafter, the classification engine 660 may be automatically updated, without user intervention, depending on the findings by the training engine.

VIII. SECOND EMBODIMENT FOR A CLASSIFICATION ENGINE UPDATE SCHEME

More specifically, according to another illustrative embodiment, malware may be discovered through a two-stage process in the threat detection platform 150, including the static analysis engine 120 and the dynamic analysis engine 160. Herein, the static analysis engine 120, upon determining that a suspect object is suspicious (e.g., exceeds a certain likelihood that the object is malicious), submits the suspect object for behavior analysis by processing this object in a run-time (virtual) environment. After behavioral analysis, the object may be classified as malicious or non-malicious.

If the initial static analysis determines that an object is not malicious, the object may be further analyzed through a secondary static analysis operable after the behavioral analysis, which extracts and analyzes relevant features of the object. The relevant features include those that may have been obfuscated during the initial static analysis but manifested themselves during execution (e.g., due to encryption or other encoding). Maintained within the threat detection platform 150 or located in the cloud, as shown, the classification engine 140 associated with the secondary static analysis may be configured to determine if the object is malicious by evaluating each feature and pattern of features received from the secondary static analysis engine.

As before, this classification engine 140 may use a decision-tree learning algorithm as a predictive model, where the decision-tree learning algorithm may be developed using machine learning techniques from prior analysis of labelled and unlabeled malware and benign objects and/or experiential knowledge from human analysts. Herein, the classification engine 140 computes a score associated with the features and pattern of features reflecting the probability that the object is malicious. Once the score for the features has been determined, the classification engine 140 may transmit that score to the dynamic analysis engine 160 to be used in the analysis of the object or may transmit information to the training engine 130 to modify the predictive model to account for malicious detection discrepancies, as described above.

According to another embodiment of the disclosure, where the object is determined to be malicious by the first detection engine 122 (e.g., static analysis engine) and is classified by the platform-based classification engine 140 as malicious by assigning a confidence score (e.g., a value representing a probability of the object being malicious), but the confidence score fails to exceed a prescribed threshold score, the above-described information associated with the object may also be provided to the training engine 130. Concurrently, the object and results by the static analysis engine 120 are provided to the dynamic engine 160 for analysis.

The training engine 130 is responsible for generating a new feature-specific predictive (reference) model from features and patterns of features identified through actual static analysis of the object, but for this embodiment, where a “current” predictive model used in the platform-based classification engine 140 determines that the object is malicious. For this embodiment, results produced by a test analysis conducted in accordance with the reference model, is compared to results produced by a test analysis conducted in accordance with the current predictive model. The comparison is conducted to assess whether the two results yield substantially different scores related to the probability that the object is malicious. If the difference in scores exceeds a threshold, the current predictive model may be modified to reflect the reference model, at least with respect to the features or pattern of features identified in the static analysis.

In arriving at the scores prescribed by the reference model, the following operations may be practiced. The current predictive model may yield, for example, a score of “80” for the object, where any score over “75” denotes that the object is to be classified by malicious. Since an object is classified as malicious, it may be deemed to deserve an overall score of “100”, and thus, the difference is determined to be “20” (100 minus 80). If the threshold for updating the predictive model is 15, for example, the predictive model associated with the classification engine requires updating with the reference model or modification of the current predictive model in accordance with the generated updates. The updates may be achieved by simply (1) decomposing that “100” score and (2) assigning component scores to each feature or pattern of features so as to yield a higher score for some than that associated with the feature (or pattern) by the current predictive model. For example, if the current predictive model associates a score of 30 with a particular feature (e.g., length of a string) identified in the object, but the reference model determines that that string is a stronger indicator of maliciousness, and accords this feature with a score of 40, the predictive model is modified by changing the associated score from 30 to 40 for future analysis of object. This approach is not dependent on the type of object analyzed, which may be an Office® document, PDF file, or JAR files, for example.

In the foregoing description, the invention is described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. 

What is claimed is:
 1. An apparatus comprising: one or more processors; and a non-transitory storage medium communicatively coupled to the one or more processors, the non-transitory storage medium comprises a first analysis engine that, during execution by the one or more processors, analyzes an object to determine if one or more features of the object indicate that the object is malicious, and a second analysis engine that, during execution by the one or more processors, receives results of the analysis of the object conducted by the first analysis engine, and analyzes, based at least in part on the results from the first analysis engine, whether the object is malicious in accordance with a predictive model, wherein, in response to the first analysis engine and the second analysis engine differing in a determination as to whether the object is classified as malicious, uploading information associated with an analysis of the object by at least one of the first analysis engine and the second analysis engine for determining whether an update of the predictive model is to occur, the update of the predictive model being trained using one or more features of the object.
 2. The apparatus of claim 1, wherein the second analysis engine further receives the update of the predictive model in response to the first analysis engine determining that the object is malicious while the second analysis engine determining that the object is non-malicious.
 3. The apparatus of claim 1, wherein the second analysis engine further receives the update of the predictive model in response to (i) a confirmation that the apparatus subscribes to a service that automatically updates predictive models used by the second analysis engine and (ii) the first analysis engine determines that the object is malicious while the second analysis engine determines that the object is non-malicious.
 4. The apparatus of claim 1, wherein the first analysis engine and the second analysis engine are part of a static analysis engine that performs pattern checking operations on the object including heuristic or determinative rule-based analysis.
 5. The apparatus of claim 4, wherein the one or more features includes information associated with the object obtained from at least the first analysis engine.
 6. The apparatus of claim 5, wherein the first analysis engine is part of a static analysis engine.
 7. The apparatus of claim 1, wherein the first analysis engine is part of a static analysis engine and the second analysis engine is part of a dynamic analysis engine, the dynamic analysis engine includes one or more virtual machines that process the object and are configured in accordance with one or more software configurations.
 8. The apparatus of claim 1, wherein the uploaded information is transmitted to a cloud computing service and comprises (1) an identifier of the object, and (2) the one or more features of the object for use by the predictive model to classify the object as malicious or non-malicious.
 9. The apparatus of claim 8, wherein the uploaded information further comprises (3) results from a preliminary classification of the object by the second analysis engine.
 10. The apparatus of claim 8, wherein the identifier of the object is a hash value of the object.
 11. The apparatus of claim 8, wherein the uploaded information further comprises (3) the results from a preliminary classification of the object by the first analysis engine.
 12. The apparatus of claim 1, wherein the first analysis engine and the second analysis engine differing in the determination as to whether the object is classified as malicious when the detection engine determines that the object is associated with a first level of maliciousness and the classification engine determines that the object is associated with a second level of maliciousness, the second level of maliciousness differing from the first level of maliciousness by at least a prescribed threshold.
 13. The system of claim 1, wherein the one or more features includes information associated with the object obtained from static analysis of the object.
 14. An apparatus comprising: one or more processors; and a memory coupled to the one or more processors, the memory comprises a detection engine that, when executed by the one or more processors, analyzes an object to determine whether the object includes one or more features that indicate the object is malicious; and a classification engine that, when executed by the one or more processors, analyzes whether the object is malicious in accordance with a predictive model maintained at a cloud computing service based at least in part on results from the detection engine, wherein, in response to the detection engine and the classification engine differing in a determination as to whether the object is malicious, uploading information associated with at least a portion of results from the analysis of the object by at least one of the detection engine and the classification engine for determining whether an update of the predictive model is to occur, the update of the predictive model being received from the cloud computing device by the classification engine.
 15. The apparatus of claim 14, wherein the classification engine to receive the update of the predictive model subsequent and in response to the detection engine determining that the object is malicious and the classification engine determining that the object is non-malicious.
 16. The apparatus of claim 14, wherein the classification engine to receive the update of the predictive model subsequent and in response to (i) the apparatus subscribing to a service that automatically updates predictive models used by the classification engine and (ii) the detection engine determining that the object is malicious and the classification engine determining that the object is non-malicious.
 17. The apparatus of claim 14, wherein the detection engine is part of a static analysis engine and the classification engine is part of a dynamic analysis engine, the dynamic analysis engine includes one or more virtual machines that process the object and are configured in accordance with one or more software configurations.
 18. The apparatus of claim 14, wherein the uploaded information comprises (1) an identifier of the object, and (2) one or more features of the object that can be used by the predictive model to classify the object as malicious.
 19. The apparatus of claim 18, wherein the uploaded information further comprises (3) the results from a preliminary classification of the object by the classification engine that include a confidence score that identifies a likelihood of the object being malicious.
 20. The apparatus of claim 14, wherein the detection engine and the classification engine differing in the determination as to whether the object is malicious when the detection engine determines that the object is associated with a first level of maliciousness and the classification engine determines that the object is associated with a second level of maliciousness, the second level of maliciousness differing from the first level of maliciousness by at least a prescribed threshold.
 21. An apparatus comprising: a detection engine including circuitry that analyzes an object to determine if one or more features of the object indicate that the object is malicious; and a classification engine communicatively coupled to the detection engine, the classification engine being configured to (i) receive results of the analysis of the object conducted by the detection engine, (ii) determine, based at least in part on the results from the detection engine and in accordance with values assigned to different parameters of a predictive model to identify features of the object that tend to be associated with malware and a confidence score associated with the object, the confidence score corresponds to a probability of the object being malicious, wherein, in response to the detection engine and the classification engine differing in a determination as to whether the object is classified as malicious, uploading information including at least the features of the object and the confidence score to cloud computing services for training a reference model to be returned to the classification engine upon determining that an update of values associated with one or more parameters of the predictive model is needed.
 22. The apparatus of claim 21, wherein the classification engine to receive the update of the values associated with the one or more parameters of the predictive model subsequent and in response to the detection engine determining that the object is malicious and the classification engine determining that the object is non-malicious.
 23. The apparatus of claim 21, wherein the detection engine and the classification engine differing in the determination as to whether the object is classified as malicious when the detection engine determining that the object is associated with a first level of maliciousness and the classification engine determining that the object is associated with a second level of maliciousness, the second level of maliciousness differing from the first level of maliciousness by at least a prescribed threshold.
 24. The apparatus of claim 21, wherein the classification engine to receive the update of the values associated with the one or more parameters of the predictive model subsequent and in response to (i) the apparatus subscribing to a service that automatically updates predictive models used by the classification engine and (ii) the detection engine determining that the object is malicious and the classification engine determining that the object is non-malicious.
 25. The apparatus of claim 21, wherein the detection engine is part of a static analysis engine and the classification engine is part of a dynamic analysis engine, the dynamic analysis engine includes one or more virtual machines that process the object and are configured in accordance with one or more software configurations. 